Home area networking (HAN) with low power considerations for battery devices

ABSTRACT

Disclosed are apparatus and methodology subject matters for providing communications to battery powered metrology devices within an Advanced Metering System (AMS). The battery powered metrology devices may be associated with AC supplied devices that are configured with mailboxes for their associated battery powered devices. The battery powered metrology devices may include such as water and gas meters collocated with electricity meters. Communications between the battery powered devices and their associated mailbox containing electricity meters may be by way of direct wired or radio frequency connections for providing reliable message transport between communications system coupled components in an Advanced Metering System.

PRIORITY CLAIM

This application claims the benefit of previously filed U.S. Provisional Patent Application entitled “HOME AREA NETWORKING (HAN) WITH LOW POWER CONSIDERATIONS FOR BATTERY DEVICES,” assigned U.S. Ser. No. 60/845,060, filed Sep. 15, 2006, and which is hereby incorporated herein by reference in its entirety for all purposes.

FIELD OF THE INVENTION

The present technology relates to utility meter communication networks. More particularly, the present technology relates to apparatus and methodologies for providing reliable message transport between communications system coupled components in an Advanced Metering System (AMS).

BACKGROUND OF THE INVENTION

The general object of metrology is to monitor one or more selected physical phenomena to permit a record of monitored events. Such basic purpose of metrology can be applied to a variety of metering devices used in a number of contexts. One broad area of measurement relates, for example, to utility meters. Such role may also specifically include, in such context, the monitoring of the consumption or production of a variety of forms of energy or other commodities, for example, including but not limited to, electricity, water, gas, or oil.

More particularly concerning electricity meters, mechanical forms of registers have been historically used for outputting accumulated electricity consumption data. Such an approach provided a relatively dependable field device, especially for the basic or relatively lower level task of simply monitoring accumulated kilowatt-hour consumption.

The foregoing basic mechanical form of register was typically limited in its mode of output, so that only a very basic or lower level metrology function was achieved. Subsequently, electronic forms of metrology devices began to be introduced, to permit relatively higher levels of monitoring, involving different forms and modes of data.

In the context of electricity meters specifically, for a variety of management and billing purposes, it became desirable to obtain usage data beyond the basic kilowatt-hour consumption readings available with many electricity meters. For example, additional desired data included rate of electricity consumption, or date and time of consumption (so-called “time of use” data). Solid state devices provided on printed circuit boards, for example, utilizing programmable integrated circuit components, have provided effective tools for implementing many of such higher level monitoring functions desired in the electricity meter context.

In addition to the beneficial introduction of electronic forms of metrology, a variety of electronic registers have been introduced with certain advantages. Still further, other forms of data output have been introduced and are beneficial for certain applications, including wired transmissions, data output via radio frequency transmission, pulse output of data, and telephone line connection via such as modems or cellular linkups.

The advent of such variety and alternatives has often required utility companies to make choices about which technologies to utilize. Such choices have from time to time been made based on philosophical points and preferences and/or based on practical points such as, training and familiarity of field personnel with specific designs.

Another aspect of the progression of technology in such area of metrology is that various retrofit arrangements have been instituted. For example, some attempts have been made to provide basic metering devices with selected more advanced features without having to completely change or replace the basic meter in the field. For example, attempts have been made to outfit a basically mechanical metering device with electronic output of data, such as for facilitating radio telemetry linkages.

Another aspect of the electricity meter industry is that utility companies have large-scale requirements, sometimes involving literally hundreds of thousands of individual meter installations, or data points. Implementing incremental changes in technology, such as retrofitting new features into existing equipment, or attempting to implement changes to basic components which make various components not interchangeable with other configurations already in the field, can generate considerable industry problems.

Electricity meters typically include input circuitry for receiving voltage and current signals at the electrical service. Input circuitry of whatever type or specific design for receiving the electrical service current signals is referred to herein generally as current acquisition circuitry, while input circuitry of whatever type or design for receiving the electrical service voltage signals is referred to herein generally as voltage acquisition circuitry.

Electricity meter input circuitry may be provided with capabilities of monitoring one or more phases, depending on whether monitoring is to be provided in a single or multiphase environment. Moreover, it is desirable that selectively configurable circuitry may be provided so as to enable the provision of new, alternative or upgraded services or processing capabilities within an existing metering device. Such variations in desired monitoring environments or capabilities, however, lead to the requirement that a number of different metrology configurations be devised to accommodate the number of phases required or desired to be monitored or to provide alternative, additional or upgraded processing capability within a utility meter.

More recently a new ANSI protocol, ANSI C12.22, is being developed that may be used to permit open protocol communications among metrology devices from various manufacturers. C12.22 is the designation of the latest subclass of the ANSI C12.xx family of Meter Communication and Data standards presently under development. Presently defined standards include ANSI C12.18 relating to protocol specifications for Type 2 optical ports; ANSI C12.19 relating to Utility industry Meter Data Table definitions; and ANSI C12.21 relating to Plain Old Telephone Service (POTS) transport of C12.19 Data Tables definition. It should be appreciated that while the remainder of the present discussion may describe C12.22 as a standard protocol, that, at least at the time of filing the present application, such protocol is still being developed so that the present disclosure is actually intended to describe an open protocol that may be used as a communications protocol for networked metrology and is referred to for discussion purposes as the C12.22 standard or C12.22 protocol.

C12.22 is an application layer protocol which provides for the transport of C12.19 data tables over any network medium. Current standards for the C12.22 protocol include: authentication and encryption features; addressing methodology providing unique identifiers for corporate, communication, and end device entities; self describing data models; and message routing over heterogeneous networks.

Much as HTTP protocol provides for a common application layer for web browsers, C12.22 provides for a common application layer for metering devices. Benefits of using such a standard include the provision of: a methodology for both session and session-less communications; common data encryption and security; a common addressing mechanism for use over both proprietary and non-proprietary network mediums; interoperability among metering devices within a common communication environment; system integration with third-party devices through common interfaces and gateway abstraction; both 2-way and 1-way communications with end devices; and enhanced security, reliability and speed for transferring meter data over heterogeneous networks.

To understand why utilities are keenly interested in open protocol communications; consider the process and ease of sending e-mails from a laptop computer or a smart phone. Internet providers depend on the use of open protocols to provide e-mail service. E-mails are sent and received as long as e-mail addresses are valid, mail boxes are not full, and communication paths are functional. Most e-mail users have the option of choosing among several internet providers and several technologies, from dial-up to cellular to broadband, depending mostly on the cost, speed, and mobility. The e-mail addresses are in a common format, and the protocols call for the e-mail to be carried by communication carriers without changing the e-mail. The open protocol laid out in the ANSI C.12.22 standard provides the same opportunity for meter communications over networks.

In addition, the desire for increased processing capabilities as well as other considerations including, but not limited to, a desire to provide reliable transportation of communications between communications systems in an Advanced Metering System (AMS) that may include a variety of consumption monitoring devices, leads to requirements for supplying communications capabilities to a significant number of meters that may be installed over a significant area often encompassing many square miles and having various data transmission and communications capabilities.

As such, it is desired to provide a universal metrology technology and associated methodology that permits transportation of communications within a metrology system including various types of metrology components including not only electricity meters, but also other types including water, gas, and oil. While various aspects and alternative embodiments may be known in the field of utility metering, no one design has emerged that generally encompasses the above-referenced characteristics and other desirable features associated with utility metering technology as herein presented.

SUMMARY OF THE INVENTION

In view of the recognized features encountered in the prior art and addressed by the present subject matter, an improved apparatus and methodology for providing reliable message delivery between Collection Engine host processors and other network nodes has been provided.

In an exemplary arrangement, a methodology has been provided to provide different low level network transport layers using common interfaces.

In one of its simpler forms, the present technology provides for the use of residential or customer premises electricity meters to provide communications between a Collection Engine and differing network nodes depending on network and node communication requirements.

One positive aspect of this type of arrangement is that reliable message delivery can be achieve with differing low level transport layers by using a common network node as a communications relay for other nodes not necessarily in constant communication with the network.

Another positive aspect of this communication methodology is that it improves opportunities to receive exception reports from end devices.

Yet another positive aspect of this type of arrangement is that selected battery powered nodes may be able to provide extended operational capabilities.

One present exemplary embodiment of the present subject matter relates to a utility meter network, comprising a plurality of individually addressable utility meters of a first type configured as nodes on the network; a plurality of individually addressable utility meters of a second type configured as nodes on the network; a memory device, associated with selected of the first type of utility meters, and with a portion of such memory device configured to serve as a mailbox for a selected one of the second type of utility meters; a collection engine associated with the network and configured to transmit messages to the nodes on the network; and a protocol stack. Preferably, such protocol stack is associated with the network and configured to construct a node path for a message transmission addressed to a selected one of the plurality of individually addressable utility meters of a second type. With such an exemplary present arrangement, transmission of redundant messages to others of the plurality of individually addressable utility meters of a first type and others of the plurality of individually addressable utility meters of a second type is avoided.

In other present alternatives of the foregoing exemplary present embodiment, such an exemplary utility meter network may further be provided with a plurality of individually addressable utility meters of a third type configured as nodes on the network; and a portion of the memory device may preferably be configured to serve as a mailbox for a selected one of such third type of utility meters.

In still further present exemplary alternatives, the plurality of individually addressable utility meters of a first type may comprise electricity meters, while the plurality of individually addressable utility meters of a second type may comprise battery powered meters selected from the group consisting of water meters, gas meters, and oil meters.

In certain of the foregoing present exemplary arrangements, the plurality of individually addressable electricity meters and/or battery powered meters may respectively incorporate a metrology portion, a register portion, at least one radio frequency interface, and an option slot, whereby alternative communications options for each such respective meter may be provided by coupling alternative communications modules to the respective option slot thereof.

In other present alternative embodiments, a meter network with low power considerations for battery supported devices associated with utility meter network communications, may be provided for providing reliable message transport between communications system coupled components in an advanced metering system including a plurality of types of consumption monitoring devices. Such an exemplary meter network may preferably comprise a plurality of individually addressable electricity meters of a first type configured as nodes on the network; a plurality of individually addressable battery powered meters of a second type configured as nodes on the network, with such plurality of individually addressable battery powered meters selected from the group consisting of water meters, gas meters, and oil meters; a memory device, associated with selected of the first type of utility meters, and with a portion of such memory device configured to serve as a mailbox for a selected one of the second type of meters; a collection engine and an associated protocol stack. Preferably, such collection engine of the foregoing exemplary embodiment is capable of integrating Radio, PLC, and IP connected meters, and configured to transmit messages to the nodes on the network. Still further, such associated protocol stack is preferably operative for preconstructing a node path for a message transmission addressed to a selected one of the plurality of individually addressable meters of a second type using different low level network transport layers using common interfaces, and for broadcasting a message in accordance with such preconstructed node path. With the foregoing exemplary present embodiment, the preconstructed node path provides a communications path without creating redundant messages to others of the plurality of individually addressable meters of a first type and others of the plurality of individually addressable meters of a second type.

It is to be understood that the present subject matter equally involves corresponding present methodology. One example of such present methodology relates to a method for providing utility meter network communications. Such an exemplary methodology preferably may include providing a plurality of individually addressable utility meters of a first type as network nodes; providing a plurality of individually addressable utility meters of a second type as network nodes; associating a memory device with selected of the first type of utility meters; configuring a portion of the memory device to serve as a mailbox for a selected one of the second type of utility meters; constructing a node path for a message transmission addressed to a selected one of the plurality of individually addressable utility meters of a second type; and broadcasting a message in accordance with the node path. With such exemplary methodology, transmission of redundant messages to others of the plurality of individually addressable utility meters of a first type and others of the plurality of individually addressable utility meters of a second type is avoided.

It is to be understood that such exemplary methodology may alternatively be practiced in accordance with additional method steps and aspects, as otherwise disclosed herein, for forming yet further present exemplary embodiments of the present subject matter.

Still further, other present exemplary methodology subject matter more particularly relates to a method for providing home area networking with low power considerations for battery supported devices associated with utility meter network communications, for providing reliable message transport between communications system coupled components in an advanced metering system including a plurality of types of consumption monitoring devices. Such exemplary present methodology may comprise providing a plurality of individually addressable electricity meters of a first type as network nodes; providing a plurality of individually addressable battery powered meters of a second type as network nodes, with such plurality of individually addressable battery powered meters selected from the group consisting of water meters, gas meters, and oil meters; associating a memory device with selected of the first type of meters; configuring a portion of the memory device to serve as a mailbox for a selected one of the second type of meters; providing a communications network operating on an open meter communications protocol, and having a collection engine capable of integrating Radio, PLC, and IP connected meters, and operative for preconstructing a node path for a message transmission addressed to a selected one of the plurality of individually addressable meters of a second type using different low level network transport layers using common interfaces; and broadcasting a message in accordance with the preconstructed node path, so that such preconstructed node path provides a communications path without creating redundant messages to others of the plurality of individually addressable meters of a first type and others of the plurality of individually addressable meters of a second type.

Still further, such exemplary methodology may be utilized in accordance with additional present method steps and aspects herein, for forming further present exemplary methodologies. For example, such foregoing methodology may alternatively be additionally practiced with an aspect of providing a wake up cycle of the battery powered meters which is controlled in order to conserve battery power thereof.

Still further alternatively, the foregoing methodology may additionally comprise providing a plurality of individually addressable meters of a third type as network nodes; configuring a portion of the memory device to serve as a mailbox for a selected one of such third type of utility meters; providing at least one relay device for transmission of messages to selected of the plurality of the meters of the first type, such at least one relay device comprising at least one of a radio relay device and a power line carrier relay device; and coupling the at least one relay device to a public backhaul.

Additional objects and advantages of the present subject matter are set forth in, or will be apparent to, those of ordinary skill in the art from the detailed description herein. Also, it should be further appreciated that modifications and variations to the specifically illustrated, referred and discussed features and elements hereof may be practiced in various embodiments and uses of the present subject matter without departing from the spirit and scope of the subject matter. Variations may include, but are not limited to, substitution of equivalent means, features, or steps for those illustrated, referenced, or discussed, and the functional, operational, or positional reversal of various parts, features, steps, or the like.

Still further, it is to be understood that different embodiments, as well as different presently preferred embodiments, of the present subject matter may include various combinations or configurations of presently disclosed features, steps, or elements, or their equivalents including combinations of features, parts, or steps or configurations thereof not expressly shown in the figures or stated in the detailed description of such figures. Additional embodiments of the present subject matter, not necessarily expressed in the summarized section, may include and incorporate various combinations of aspects of features, components, or steps referenced in the summarized objects above, and/or other features, components, or steps as otherwise discussed in this application. Those of ordinary skill in the art will better appreciate the features and aspects of such embodiments, and others, upon review of the remainder of the specification.

BRIEF DESCRIPTION OF THE DRAWINGS

A full and enabling disclosure of the present subject matter, including the best mode thereof, directed to one of ordinary skill in the art, is set forth in the specification, which makes reference to the appended figures, in which:

FIG. 1 is a block diagram overview illustration of an Advanced Metering System (AMS) in accordance with the present subject matter;

FIG. 2 illustrates an exemplary Advanced Metering System deployment incorporating various methodology aspects of the present subject matter;

FIG. 3 illustrates a block diagram of an exemplary meter incorporating interface features in accordance with the present subject matter; and

FIG. 4 is a flow chart illustrating presently disclosed exemplary methodology whereby redundant transmission of redundant messages within a node path may be avoided.

Repeat use of reference characters throughout the present specification and appended drawings is intended to represent same or analogous features or elements of the present subject matter.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

As discussed in the Summary of the Invention section, the present subject matter is particularly concerned with an improved apparatus and methodology for providing reliable message delivery between the Collection Engine host processors and other network nodes.

Selected combinations of aspects of the disclosed technology correspond to a plurality of different embodiments of the present subject matter. It should be noted that each of the exemplary embodiments presented and discussed herein should not insinuate limitations of the present subject matter. Features or steps illustrated or described as part of one embodiment may be used in combination with aspects of another embodiment to yield yet further embodiments. Additionally, certain features may be interchanged with similar devices or features not expressly mentioned which perform the same or similar function.

Reference will now be made in detail to the presently preferred embodiments of the subject home area network methodology and apparatus. Referring now to the drawings, FIG. 1 is a block diagram overview illustration of an Advanced Metering System (AMS) in accordance with the present subject matter.

Advanced Metering System (AMS) 100 in accordance with the present subject matter is designed to be a comprehensive system for providing advanced metering information and applications to utilities. AMS 100 is built around industry standard protocols and transports, and is designed to work with standards compliant components from third parties.

Major components of AMS 100 include meters 142, 144, 146, 148, 152, 154, 156, 158; one or more radio networks including RF neighborhood area network (RF NAN) 162 and accompanying Radio Relay 172 and power line communications neighborhood area network (PLC NAN) 164 and accompanying PLC Relay 174; an IP based Public Backhaul 180; and a Collection Engine 190. Other components within AMS 100 include a utility LAN 192 and firewall 194 through which communications signals to and from Collection Engine 190 may be transported from and to meters 142, 144, 146, 148, 152, 154, 156, 158 or other devices including, but not limited to, Radio Relay 172 and PLC Relay 174.

AMS 100 is configured to be transportation agnostic or transparent; such that meters 142, 144, 146, 148, 152, 154, 156, 158 may be interrogated using Collection Engine 190 regardless of what network infrastructure lay in between. Moreover, due to this transparency, the meters may also respond to Collection Engine 190 in the same manner.

As illustrated in FIG. 1, Collection Engine 190 is capable of integrating Radio, PLC, and IP connected meters. To facilitate this transparency, AMS 100 uses ANSI C12.22 meter communication protocol for networks. C12.22 is a network transparent protocol, which allows communications across disparate and asymmetrical network substrates. C12.22 details all aspects of communications, allowing C12.22 compliant meters produced by third parties to be integrated into a single advanced metering interface (AMI) solution. AMS 100 is configured to provide meter reading as well as load control/demand response, in home messaging, and outage and restoration capabilities. All data flowing across the system is sent in the form of C12.19 tables. The system provides full two-way messaging to every device; however, many of its functions may be provided through broadcast or multicast messaging and session-less communications.

In accordance with the present subject matter, the disparate and asymmetrical network substrates may be accommodated by way of a native network interface having the capability to plug in different low level transport layers using .NET interfaces. In accordance with an exemplary configuration, Transmission Control Protocol/Internet Protocol (TCP/IP) may be employed and the remainder of the present discussion is directed to such a choice of transport layer. It should be appreciated, however, that TCP/IP is not the only such low level transport layer protocol available and that other protocols such as User Datagram Protocol (UDP) may be used.

A Native Network Interface in accordance with the present technology provides access to the physical, i.e., native, network protocol from the C12.22 protocol stack in C12.22 Host applications. The design includes a base class for reuse in development of the transport layer. The main interface methods provide standard sessionless server and client methods for sending and receiving data although session-based communication may also be employed. The base class also includes access to a standard logging mechanism, common instrumentation through Windows Management Instrumentation (WMI), and standard status and diagnostic reporting. A static method is used to load the transport layer assembly, transparently to the client application. The transport layer assemblies may be configurable to include more control over incoming messages to accommodate variable length messages more efficiently, and provide a configurable security interface.

While data collection can be addressed by scheduling AMR nodes to connect at different times or by contacting AMR nodes individually, such a methodology would require a significant amount of time as well as a great deal of program management. The methodology in accordance with the present subject matter allows AMR responses to be distributed randomly over time, thus optimizing the use of available AMR network bandwidth while avoiding advanced management techniques.

With present reference to FIG. 2, it will be seen that an exemplary Advanced Metering System (AMS) generally 200 deployment has been illustrated. FIG. 2 illustrates for exemplary purposes only a single RF LAN cell, with multiple member nodes organized into three levels, as well as four directly connected IP meters 270, 272, 274, and 276. In such system, respective meter devices 210, 220, 230, 232, 240, 242, 250, 252, 254, 256, 260, 262, 264, 266, 270, 272, 274, and 276, Cell Relay 202, and Collection Engine 290, have C12.22 network addresses. Collection Engine 290 may in accordance with the present subject matter have multiple C12.22 addresses to allow for separate addressing between different services (functionalities). Meter (or master) data management system 292 is not part of the C12.22 network, but preferably it will be implemented so as to communicate over the Utility LAN 294 to Collection Engine 290 via Web Services. Communications between Cell Relay 202 and Utility LAN 294 variously involve Public Backhaul 280 and firewall 296, in a manner analogous to that discussed above in conjunction with Public Backhaul 180 and firewall 194 (FIG. 1), as well understood by those of ordinary skill in the art.

The meter data acquisition process begins with the Meter (or Master) Data Management System 292 initiating a request for data. Such operation is done through a web services call to Collection Engine 290 and may be performed without knowledge of the configured functionality of the end-device. Collection Engine 290 analyzes the request for data, and formulates a series of C12.22 multicast (or broadcast) data requests. Such requests are then sent out either directly to the device (in the case of an IP connected meter, such as 270), or to Cell Relay 202 that relays the message out to all appropriate nodes. Broadcast and multicast messages are sent by Cell Relay 202 to all members of the cell, either via an AMS RF LAN-level broadcast, or by the Cell Relay repeating the message. For efficiency sake, the use of an RF LAN level broadcast may be preferred.

Typically these requests are sent as a call to a manufacturer's stored procedure. In C12.22, stored procedure calls are performed as writes to a predetermined table, e.g., “table 7.” The stored procedure will send the default upload configured for such device. For example, a given meter may be configured to upload two channels of hourly interval data, plus its event history. Another meter might be programmed to send up its TOU registers. The stored procedure will require four parameters to be fully operative in accordance with the present subject matter: data start time, data end time, response start time, and response end time. The data start and end time are to be used to select which data to send. The response start time and end time are used to determine the window within which the upstream system wants to receive the data. The various AMS enabled meters of FIG. 2 are preferably field programmable, via C12.19 tables, as to the type of data to be included in a default upload.

When data is sent to Collection Engine 290, it is sent as C12.19 table self-write with the notification bit set, and the do-not-respond bit set. The result is that per the present subject matter no C12.22 acknowledgement is sent in response to the Collection Engine's broadcast, nor does the Collection Engine 290 in response to the notify-write send any response; however, the notify-write effectively serves per the present subject matter as an acknowledgement to the receipt of the broadcast.

The response processing section can use the configured data about an end device and the response message from the end device to determine the results from the device. The response processing section begins operation associated with a specific job in a task list, but can be switched between any active job that is awaiting a response. Such operation allows responses that contain logs from the device to be parsed by each job that could be waiting for an action to be completed within the end-device. Such also would allow unsolicited messages to be parsed by the IMA (Interface between Meter and Application) code and then later associated with any possible jobs, as determined by the IMA, all in accordance with the present subject matter.

While most operations will not require this, the AMS meters will support chaining a series of C12.22 Extended Protocol Specification for Electronic Metering (EPSEM) messages, such as multiple table reads and writes in a single request. This is functionality that is required in the C12.22 specification, and will assist in improving the efficiency of the system, as it avoids the overhead of sending a separate message for each EPSEM command. AMS enabled devices will process each request sequentially, allowing a series of operations to be handled in a single command, each building on the next, such that a read subsequent to a write would reflect the results of the request write. If a command in an EPSEM chain cannot be completed, remaining commands in the chain are rejected with appropriate error messages, per the present subject matter.

When a respective device receives a request, it evaluates the multi-cast address specified. If the device is a member of the multicast group, it responds to the request; otherwise, it discards it. Membership in different multicast groups is determined via use of C12.22 standard table 122.

On-demand reading per the present subject matter is similar to the Daily Meter Data Acquisition Process; however, rather than sending a broadcast or multicast request, the on-demand reading process in accordance with the present subject matter communicates directly to desired respective meters. Such process begins with a user initiated on-demand read through an AMS User Interface, or through a web services call from an upstream system. Per the present subject matter, an orchestration layer of the Collection Engine 290 begins by evaluating the current system load of the communications substrate through which the respective device is connected. Requests for an on-demand read from a saturated cell may be rejected.

Once Collection Engine 290 determines that the request can be honored, it selects per the present subject matter an appropriate communication server within the Collection Engine, and submits the command to retrieve data from the device and return it. The communications server forms a C12.22 table read request, encrypts it, and sends it to the device directly, if IP connected, or to Cell Relay 202 for RF LAN connected devices. In cases where traffic flows through the RF LAN, the Cell Relay software retrieves the message from the IP backhaul 280, and evaluates the message. The destination address (in C12.22 terminology, the called ApTitle) may be stripped off to save bandwidth on the network, relying instead on the underlying RF LAN addressing scheme for delivering the message. The Cell Relay software must also examine whether the destination ApTitle is still valid within the cell. If the destination ApTitle is no longer valid, the Cell Relay rejects the message, returning an error packet to the Collection Engine. Provided that the destination is still valid, the Cell Relay software sends the message to the device across the RF LAN, per the present subject matter.

In accordance with present technology, several of the groupings of meters illustrated in FIG. 2 may correspond to various types of meters at or near a residence or customer premises that may take advantage of the AMS communication system of the present subject matter to form a home area network. In particular, Meters 230, 232, 240, and 242 may correspond to electricity meters in a meter group; meters 250, 254, 260, and 264 may correspond to water meters associated with meters 230, 232, 240, and 242 respectively and meters 252, 256, 262, and 266 may correspond to gas meters associated with meters 230, 232, 240, and 242 respectively.

According to present technology, electricity meters 230, 232, 240, and 242 may include communications equipment that is constantly energized by way of the individual meters connection to a source of alternating current (AC) electricity. Meters 250, 252, 254, 256, 260, 262, 264, and 266, on the other hand, are not coupled to an AC source but rather their communications equipment may be supplied by way of an onboard battery power supply. In this manner, electricity meters 230, 232, 240, and 242 form hubs for a home area network through which meters 250, 252, 254, 256, 260, 262, 264, and 266 may communicate with Collection Engine 290 or other network nodes. Such other network nodes may include other types of devices residing within a residence or customer premises including devices such as, but not limited to, appliances, display devices, and electronic control devices.

In order to conserve battery power, battery operated meters 250, 252, 254, 256, 260, 262, 264, and 266 may be associated with the respective electricity meters 230, 232, 240, and 242 so that communications between battery powered meters 250, 252, 254, 256, 260, 262, 264, and 266 may be conducted with Collection Engine 290 by way of the respective electricity meters 230, 232, 240, and 242 by providing in the electricity meters dedicated portions of memory configured to serve as “mailboxes” for the battery powered meters 250, 252, 254, 256, 260, 262, 264, and 266.

When, for example, a message is broadcast, multicast, or specifically addressed to an individual network node (meter), a protocol stack for the RF LAN advantageously takes the message and constructs a node path for the message to take before actually transmitting the packet. Such pre-constructed node path allows Cell Relay 202 per the present subject matter to push a message down through the tree of the cell without creating redundant radio messages.

If Collection Engine 290 wants to do an on-demand read to gas meter 256, it starts by sending the message to Cell Relay 202. Cell Relay 202 in turn sends out a transmission that will be heard by both respective electricity meters 210 and 220 (in the exemplary configuration of present FIG. 2). Meter 220 could go ahead and retransmit the message, but this would not get the message to gas meter 256. Instead, it would simply waste bandwidth. With the node path provided by the RF LAN protocol stack, meters 210 and 220 will hear the message, but per the present subject matter only meter 210 will retransmit the message. The retransmitted message of meter 210 will be heard by both meters 230 and 232, but only meter 232 will be in the node path, again meaning other parts of the cell (such as meters 250 and 252) will not receive a message that would be useless to them.

In accordance with the present technology, electricity meter 232 has contained therein dedicated storage space configured to operate as a mailbox for gas meter 256 as well as water meter 254 and possibly an oil meter (not illustrated) or other home area network devices including such as might be installed separately within a residence or customer premises. As the battery operated meters associated with electricity meter 232, in this case meters 254 and 256, are configured to “wake up” only periodically in order to save battery power, the mailbox in electricity meter 232 associated with gas meter 256 will store any message directed to gas meter 256's address until such time as gas meter 256 wakes up and checks its mail in its mailbox. The mailbox may also store messages sent from the gas meter 256 or any other home area network device until such time as the message may be forwarded to Collection Engine 290 or other network address.

Once the message is received at gas meter 256, the meter must unpack the request and act on it. The communications module within the device will pull the C12.22 message out of its mailbox housed on electricity meter 232 and provide it to its Register Board 320 (FIG. 3). Register Board 320 will decrypt the message based on shared keys, and then respond to the request, encrypting it and returning it to the calling ApTitle either directly via the RF LAN (as the gas meter 256 is now awake) or by way of its mailbox for later delivery. In the case of the RF LAN, the message is simply forwarded to the next layer up in the cell. Messages are forwarded from one layer to the next until they finally reach Cell Relay 202, which relays it across the IP backhaul 280 to the communications server that initiated the transaction.

With reference now to FIG. 3, there is illustrated a block diagram of an exemplary meter 300 incorporating interface features in accordance with the present subject matter. Meter 300 incorporates several major components including metrology 310, a register board 320 and one or more communications devices. In the presently illustrated configuration, meter 300 may include an RF LAN Interface 330 and accompanying antenna 332 and a Zigbee Interface 340 and its accompanying antenna 342. In addition, an Option Slot 350 may be provided to accommodate a third party network or communications module 352.

Metrology 310 may correspond to a solid-state device configured to provide an internal C12.18 blurt communications to register board 320. Communications within meter 300 is conducted via C12.22 Extended Protocol Specification for Electronic Metering (EPSEM) messages. The meter register board 320 is configured to fully support C12.19 tables and C12.22 extensions. While all meter data will be accessible via standard C12.19 tables, in order to facilitate very low bandwidth communications, manufacturers tables or stored procedures are included which provide access to specific time-bound slices of data, such as the last calendar day's worth of interval data or other customized “groupings” of data.

Meter 300 may be variously configured to provide differing communications capabilities depending on whether the metrology is designed for electricity meters and thus has available a continuously available AC supply source or is configured as a battery operated device to be activated for communications sessions on an intermittent or scheduled basis. In exemplary configurations, one or more of GPRS, Ethernet, and RF LAN communications modules may be provided. GPRS will allow meters to be IP addressable over a public backhaul and provide more bandwidth than the meter will ever require, but may incur ongoing subscriptions costs. Ethernet connectivity can be used to bridge to third party technologies, including WiFi, WiMax, in-home gateways, and BPL, without integrating any of these technologies directly into the metering device, but with the tradeoff of external wiring and a two part solution. Ethernet devices may be used primarily in pilots and other special applications; though they may be ideal for certain high-density RF-intolerant environments such as meter closets.

Due to the increased complexity of managing a WAN interface, with its more sophisticated link negotiation requirements and TCP/IP stack, WAN connected meters may include an additional circuit board dedicated to WAN connectivity. This board will interface with meter 300 using EPSEM messages and Option Slot 350.

The availability of Option Slot 350 within meter 300 provides the advantage that it will make meter 300 available for integration with third party backhauls, such as PLC. In order for such third party devices to be integrated into AMS 100, on the other hand, third party devices will need to include both a communications board and a C12.22 compliant relay to couple communications signals from the third party's proprietary network to an IP connection. Alternatively, third parties could integrate meter 300 into their own end-to-end solution.

The communications protocol between meter 300 and communications modules 330, 340, and WAN module or optional third party communications module 352 follow the C12.22 standards, allowing any third party to design to the standard and be assured of relatively straightforward integration.

Communication to the Collection Engine 190 is performed over an Internet Protocol connection. The Wide-Area-Network is a fully routable, addressable, IP network that may involve a variety of different technologies including, but not limited to, GPRS, WiFi, WiMax, Fiber, Private Ethernet, BPL, or any other connection with sufficiently high bandwidth and ability to support full two-way IP communication. Several assumptions may be made regarding the IP WAN. Collection Engine 190 is assumed to be able to communicate directly with other nodes on the IP WAN. While communications may be conducted through a firewall 194, it is not necessary that such be proxied, unless the proxy is itself a C12.22 node functioning as a relay between a private IP network and the public IP WAN.

With present reference to FIG. 4, there is provided a flow chart generally 400 illustrating exemplary methodology whereby transmission of redundant messages within a node path may be avoided. As illustrated, at step 402 the exemplary method calls for providing a plurality of individual addressable utility meters of a first type as network nodes. At step 404 the exemplary method calls for providing a plurality of individual addressable utility meters of a second type as network nodes. As previously noted, in exemplary configurations, meters of the first type may correspond to electricity meters while meters of the second type may correspond to battery operated meters such as water, gas, and oil meters. Further in accordance with the exemplary method illustrated in flow chart 400, at step 406 a memory device is associated with selected of the first type of utility meter and in step 408 a portion of the memory device is configured to serve as a mailbox for a selected one of the second type of utility meter. The exemplary method then provides for constructing a node path in step 410 for a message transmission addressed to a selected one of the plurality of individual addressable utility meters of the second type and finally, in step 412, for broadcasting a message in accordance with the node path created in step 410.

While the present subject matter has been described in detail with respect to specific embodiments thereof, it will be appreciated that those skilled in the art, upon attaining an understanding of the foregoing may readily produce alterations to, variations of, and equivalents to such embodiments. Accordingly, the scope of the present disclosure is by way of example rather than by way of limitation, and the subject disclosure does not preclude inclusion of such modifications, variations and/or additions to the present subject matter as would be readily apparent to one of ordinary skill in the art. 

What is claimed is:
 1. A method for providing utility meter network communications, comprising: providing a plurality of individually addressable AC powered utility meters of a first type as network nodes; providing a plurality of individually addressable battery powered utility meters of a second type as network nodes; associating a memory device with selected of the first type of utility meters; configuring a portion of the memory device to serve as an associated mailbox for a selected one of the second type of utility meters to store any messages directed to an address of the selected one of the second type of utility meters; constructing a node path for a message transmission addressed to the selected one of the second type of utility meters via its associated mailbox; and broadcasting a message in accordance with the node path, wherein the selected one of the second type of utility meters is configured to check its associated mailbox maintained by the selected of the first type of utility meters for the message.
 2. A method as in claim 1, further comprising: providing a plurality of individually addressable utility meters of a third type as network nodes; and configuring a portion of the memory device to serve as a mailbox for a selected one of the third type of utility meters.
 3. A method as in claim 1, wherein providing a plurality of individually addressable utility meters of a first type comprises providing a plurality of individually addressable electricity meters.
 4. A method as in claim 1, wherein providing a plurality of individually addressable utility meters of a second type comprises providing a plurality of individually addressable battery powered meters selected from the group consisting of water meters, gas meters, and oil meters.
 5. A method as in claim 3, wherein providing a plurality of individually addressable electricity meters comprises providing a plurality of electricity meters incorporating a metrology portion, a register portion, at least one radio frequency interface, and an option slot, whereby alternative communications options may be proved by coupling alternative communications modules to the option slot.
 6. A method as in claim 4, wherein providing a plurality of individually addressable battery powered meters selected from the group comprising water meters, gas meters, and oil meters comprises providing a plurality of meters incorporating a metrology portion, a register portion, at least one radio frequency interface, and an option slot, whereby alternative communications options may be proved by coupling alternative communications modules to the option slot.
 7. A method as in claim 1, further comprising: providing at least one relay device for transmission of messages to selected of the plurality of utility meters of the first type; and coupling the at least one relay device to a public backhaul.
 8. A method as in claim 7, wherein providing at least one relay device comprises providing at least one radio relay device.
 9. A method as in claim 7, wherein providing at least one relay device comprises providing at least one power line carrier relay device.
 10. A utility meter network, comprising: a plurality of individually addressable AC powered utility meters of a first type configured as nodes on said network; a plurality of individually addressable battery powered utility meters of a second type configured as nodes on said network; a memory device, associated with selected of said first type of utility meters, and with a portion of said memory device configured to serve as an associated mailbox for a selected one of said second type of utility meters to store any messages directed to an address of the selected one of the second type of utility meters; a collection engine associated with said network and configured to transmit messages to said nodes on said network; and a protocol stack associated with said network and configured to construct a node path for a message transmission addressed to the selected one of the second type of utility meters via its associated mailbox, wherein the selected one of the second type of utility meters is configured to check its associated mailbox maintained by the selected of the first type of utility meters for the message transmission.
 11. A utility meter network as in claim 10, further comprising: a plurality of individually addressable utility meters of a third type configured as nodes on said network; and wherein a portion of said memory device is configured to serve as a mailbox for a selected one of said third type of utility meters.
 12. A utility meter network as in claim 10, wherein said plurality of individually addressable utility meters of a first type comprise electricity meters.
 13. A utility meter network as in claim 10, wherein said plurality of individually addressable utility meters of a second type comprise battery powered meters selected from the group consisting of water meters, gas meters, and oil meters.
 14. A utility meter network as in claim 12, wherein said plurality of individually addressable electricity meters respectively incorporate a metrology portion, a register portion, at least one radio frequency interface, and an option slot, whereby alternative communications options for each respective electricity meter may be provided by coupling alternative communications modules to said respective option slot thereof.
 15. A utility meter network as in claim 13, wherein said plurality of individually addressable battery powered meters respectively incorporate a metrology portion, a register portion, at least one radio frequency interface, and an option slot, whereby alternative communications options for each respective battery powered meter may be provided by coupling alternative communications modules to said respective option slot thereof.
 16. A utility meter network as in claim 10, further comprising: at least one relay device for transmission of messages to selected of said plurality of utility meters of the first type; and a public backhaul coupled to said at least one relay device.
 17. A utility meter network as in claim 16, wherein said at least one relay device comprises at least one radio relay device.
 18. A utility meter network as in claim 16, wherein said at least one relay device comprises at least one power line carrier relay device.
 19. A utility meter network as in claim 16, further comprising: a second plurality of individually addressable utility meters of the first type configured as nodes on said network and coupled directly to said public backhaul.
 20. A method for providing home area networking with low power considerations for battery supported devices associated with utility meter network communications, for providing reliable message transport between communications system coupled components in an advanced metering system including a plurality of types of consumption monitoring devices, comprising: providing a plurality of individually addressable AC powered electricity meters of a first type as network nodes; providing a plurality of individually addressable battery powered meters of a second type as network nodes, with such plurality of individually addressable battery powered meters selected from the group consisting of water meters, gas meters, and oil meters; associating a memory device with selected of the first type of meters; configuring a portion of the memory device to serve as an associated mailbox for a selected one of the second type of meters to store any messages directed to an address of the selected one of the second type of meters; providing a communications network operating on an open meter communications protocol, and having a collection engine capable of integrating Radio, PLC, and IP connected meters, and operative for preconstructing a node path for a message transmission addressed to the selected one of the second type of meters via its associated mailbox using different low level network transport layers using common interfaces; and broadcasting a message in accordance with the preconstructed node path; wherein a wake up cycle of the battery powered meters is controlled in order to conserve battery power thereof; and wherein the selected one of the second type of meters is configured to check its associated mailbox maintained by the selected of the first type of meters for the message upon waking up.
 21. A method as in claim 20, further comprising: providing a plurality of individually addressable meters of a third type as network nodes; configuring a portion of the memory device to serve as a mailbox for a selected one of such third type of meters; providing at least one relay device for transmission of messages to selected of the plurality of the meters of the first type, such at least one relay device comprising at least one of a radio relay device and a power line carrier relay device; and coupling the at least one relay device to a public backhaul.
 22. A meter network with low power considerations for battery supported devices associated with utility meter network communications, for providing reliable message transport between communications system coupled components in an advanced metering system including a plurality of types of consumption monitoring devices, comprising: a plurality of individually addressable AC powered electricity meters of a first type configured as nodes on said network; a plurality of individually addressable battery powered meters of a second type configured as nodes on said network, with such plurality of individually addressable battery powered meters selected from the group consisting of water meters, gas meters, and oil meters; a memory device, associated with selected of said first type of meters, and with a portion of said memory device configured to serve as an associated mailbox for a selected one of said second type of meters to store any messages directed to an address of the selected one of the second type of meters; and a collection engine capable of integrating Radio, PLC, and IP connected meters, and configured to transmit messages to said nodes on said network, and associated with a protocol stack operative for preconstructing a node path for a message transmission addressed to the selected one of the second type of meters via its associated mailbox using different low level network transport layers using common interfaces, and for broadcasting a message in accordance with such preconstructed node path; wherein said battery powered meters of the second type are further configured for operation per a controlled wake up cycle in order to conserve battery power thereof; and wherein the selected one of the second type of meters is configured to check its associated mailbox maintained by the selected of the first type of meters for the message upon waking up.
 23. A meter network as in claim 22, further comprising: a plurality of individually addressable meters of a third type configured as nodes on said network; at least one relay device for transmission of messages to selected of said plurality of the meters of the first type, such at least one relay device comprising at least one of a radio relay device and a power line carrier relay device; and a public backhaul coupled to said at least one relay device; and wherein a portion of said memory device is configured to serve as a mailbox for a selected one of said third type of meters. 